Rethinking Quality Studio

The problem isn't the data.
It's the language.

Today's screen is an operator console — it shows the database (steps, journeys, lenses, change-sets) and assumes you already know the model. A newcomer lands on a record list with no path and a wall of jargon.

Every direction below starts from the same fix: say what things are in plain words, and lead with the question the user actually has.

Plain-language reframe
step→Check
journey→Flow
domain→Area
change-set · cs:a8f3→Change history
generation run→AI run
process / component / live lens→removed — filters, not personas
Three jobs the UI must answer
01How healthy is my testing?
02What's broken right now?
03Generate tests for me — the actual value
Three directions follow, each leading with a different one of these jobs. Pick one — or mix. Then I'll build the chosen direction out to full fidelity across every screen.
Direction A · Health Report
Answer-first. Lands on a plain verdict, not a record list. Best for QA leads & PMs. — leads with job 01.
Quality Studio ▾ agents-studio
Coverage · Failures · History ✦ Generate tests
82% covered

Billing is in good shape — 2 checks need a look.

47 checks | 6 flows | ● 44 passing ● 2 failing ● 1 not run
By area
Authentication
91%
20 passing · 0 failing
Billing
82%
44 passing · 2 failing
Catalog
64%
16 passing · thin coverage
Run Ingestion
38%
Needs tests · Generate →
Needs attention
Charge the saved card
Failing in Complete a paid checkout · staging · 2 min ago
Failing View →
Acknowledge payment webhook
Failing in Issue a partial refund · staging · 6 hours ago
Failing View →
Direction B · Guided Workspace
Task-first. The AI action is the hero; every empty state guides you forward. Best for hands-on engineers. — leads with job 03.
Quality Studio
Overview
Coverage
Failures 2
Generate
History
System healthy
Generate

Let Studio write tests for you

It reads your code and drafts checks & flows. You review before anything is saved.

1Which area?
Run Ingestion Billing Catalog Authentication
2What should it create?
✓ Flows
End-to-end paths
✓ Checks
Individual tests
Test data
Seed fixtures
Est. cost ~$0.04 · runs in background
✦ Generate & review
Recent
Generated 8 flows for Billing· 2 min ago · ready to review
Test run failed — 2 checks· 6 hr ago
Priya tightened refund risk levels· yesterday
Direction C · Flow Map
Visual. Turns "a flow is a sequence of checks" into a picture, with status & risk on it. Best for process owners. — leads with job 02.
Quality Studio Billing › Flows
Passing Failing Not run

Complete a paid checkout

Cart → tax → charge → invoice, the happy path for a returning customer.

1 of 5 failing
PASSING
Compute cart total
High risk
PASSING
Apply a coupon
Medium risk
↳ SUB-FLOW
Authorize a card
2 checks · expand
FAILING
Charge the saved card
Critical risk
PASSING
Emit invoice PDF
Low risk
Charge the saved card is failing
expected charge.status = "settled", got "declined"
staging · 2 min ago · last passed yesterday · changed by Priya
Open run →
Navigation at scale · The persistent shell
Constant on every screen: project switcher · ⌘K search · Failures inbox · Generate. Sidebar is search-first & scoped, never a flat dump of 312 areas.
Quality Studio ▾ agents-studio
⌕ Search areas, flows, checks, runs… ⌘K
⚠ Failures 14 ✦ Generate AR
⌕ Filter areas…
★ Pinned
Billing2
Authentication
Catalog
Your team · payments
Invoicing
Run Ingestion1
Payouts
▾ All areas312
agents-studio›Billing›Flows
Views: Failing only Critical risk My team All Group: Status ▾
Failing· 1
Complete a paid checkout
5 checks · Charge the saved card failing
1 failing
Passing· 5
Issue a partial refund
3 checks · all passing
Passing
⌘K · Jump to anything
The primary way power users move at scale. One ranked search across every record type + actions.
⌕ char esc
Checks
Charge the saved card · Billing › Checkout
Failing
Charge with 3-D Secure · Billing
Flows
⇲
Authorize a charge · Billing
Areas
▦
Charging & Payments · payments team
Actions
✦Generate checks for this area…
enter open ↑↓ navigate Searches 312 areas · 1.8k flows · 9.4k checks
Failures inbox · Cross-cutting triage
The most important enterprise view: every failing check across all 312 areas in one queue — so nobody walks the tree to find problems.

Failures

14 across 6 areas
Save this view
Area: All ▾ Risk: Critical + High ▾ Owner: Any ▾ Last 24h ▾ Group by Area ▾
Billing· payments team2
Charge the saved card
Complete a paid checkout · staging · 2 min ago
Critical PK Open →
Acknowledge payment webhook
Issue a partial refund · staging · 6 hr ago
High — Open →
Run Ingestion· platform team1
Resolve test result to a check
Ingest a junit file · ci · 11 hr ago
High SM Open →